What Does This Do

Allow Maven Central deployment job to fail.

The result of this change is that the verify_maven_central_deployment job that depends on deploy_to_maven_central will run as long as deploy_to_maven_central completes. Without this change, the verify_maven_central_deployment job only runs if deploy_to_maven_central succeeds.

Motivation

With the 1.63.1 patch release, pipeline failures resulted in the successful publishing of artifacts onto Maven Central but not of OCI images. Also, OCI image publishing is gated via a publishing-job that is gated by Maven Central deployment verification.

After fixing the pipeline issue, we wanted to re-run the pipeline and override the Maven Central deployment verification to allow the OCI publishing. This should be possible with the manually triggered override_verify_maven_central job, but since deploy_to_maven_central failed (release already exists), verify_maven_central_deployment could never run.

By allowing the deployment to fail and the verification to run regardless, the override should now work.

Additional Notes

If the override job is not run and the initial deployment fails, the verification would run and still fail as well, still properly gating the publishing-gate.

The Maven Central publishing jobs only run on protected git tags.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]